home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ShareWare OnLine 2
/
ShareWare OnLine Volume 2 (CMS Software)(1993).iso
/
os2
/
os2faq_j.zip
/
OS2FAQ.1
next >
Wrap
Internet Message Format
|
1993-02-16
|
48KB
Path: nlbbs!gator!rde!uunet!ukma!netsys!pagesat!spssig.spss.com!uchinews!ellis!sip1
From: sip1@ellis.uchicago.edu (Timothy F. Sipples)
Newsgroups: comp.os.os2.misc,comp.os.os2.apps,news.answers
Subject: OS/2 Frequently Asked Questions List Rel. 2.0j (1 of 2)
Message-ID: <1993Feb6.202953.29379@midway.uchicago.edu>
Date: Sat, 6 Feb 1993 20:29:53 GMT
Expires: Thu, 15 Apr 1993 23:59:59 GMT
Sender: news@uchinews.uchicago.edu (News System)
Reply-To: sip1@midway.uchicago.edu
Followup-To: comp.os.os2.misc
Organization: Dept. of Econ., Univ. of Chicago
Lines: 1062
Approved: news-answers-request@mit.edu
Supersedes: <1993Jan9.060600.21677@midway.uchicago.edu>
Archive-name: os2-faq/user/part1
Version: 2.0j
OS/2 Frequently Asked Questions List
User's Edition
Release 2.0j
February 6, 1993
Compiled by Timothy F. Sipples
(0.0) Introduction and Credits
For changes, suggestions, or additions please mail sip1@ellis.uchicago.edu
or write:
Timothy F. Sipples
Center for Population Economics
University of Chicago
1101 East 58th Street
Chicago, IL 60637 U.S.A.
I cannot acknowledge your contribution(s), but they are greatly
appreciated.
Mention of a product does not constitute an endorsement. Customers outside
the United States should not necessarily rely on 800 telephone numbers,
part numbers, or upgrade policies contained in this List. Electronic mail
addresses are in Internet form; use addressing appropriate to your mail
system.
This List is freely distributable. If you redistribute the List, please
include all the original files. If you publish the List, in full or in
part, please forward a copy of the finished publication to Timothy F.
Sipples at the above address.
This List is updated monthly and is distributed through various computer
networks and online services, including the Internet, CompuServe, GEnie,
and many BBSes.
Both ASCII text and OS/2 Information Presentation Facility (INF) versions
of the List are provided. To view the INF version of the List, go to any
OS/2 command line prompt (e.g. double click on "OS/2 Window") and type:
VIEW OS2FAQ.INF
The ASCII text version may be viewed using any text editor, word processor,
or file listing utility. The text version is intended to answer any
questions you may have before actually obtaining and using OS/2. You will
find that the INF version provides a much more attractive List, with
hypertext links, fast indexing, and, increasingly, illustrations.
If you have not received both files (OS2FAQ.INF and OS2FAQ.TXT), please ask
your system operator to make sure he/she is receiving the correct and
complete package every month.
(0.1) Release Notes
This release is the first to include the INF version of the List, replacing
the Rich Text Format (RTF) version. This initial INF version is a bit less
polished than I would like, but I hope to enhance it substantially in the
coming months. In particular, the organization of the List will be
revised.
I hope to include revision markings in the next release. At some point in
the future I plan to add Master Help Index entries.
Please contact the author [See (0.0) Introduction and Credits] if you would
like to volunteer to redistribute the List to BIX or America Online.
Related information:
(0.0) Introduction and Credits
(0.2) Questions in this Release
(0.2) Questions in this Release
The following questions are addressed in this release:
(1.0) What is OS/2?
(1.1) What are the differences between versions?
(1.2) What is Extended Services?
(1.3) How good is OS/2 2.0's DOS and Windows compatibility?
(1.4) Where can I buy OS/2, and how much does it cost?
(1.5) What hardware do I need to run IBM OS/2 2.0? Do I need a PS/2?
(1.6) What applications are available for OS/2?
(1.7) Where can I obtain OS/2 shareware and freeware?
(1.8) I am having trouble installing OS/2 2.0. What should I do?
(1.9) Will OS/2 2.0 work with my SuperVGA adapter?
(1.10) Will OS/2 2.0 work with my printer?
(1.11) How do I access HPFS partitions on my hard drive without booting
from the hard drive? I'm getting error messages now -- how do I "repair"
my hard disk?
(1.12) I can't install OS/2 from Drive B. What's wrong?
(1.13) Is there a Norton Utilities for OS/2?
(1.14) Sometimes OS/2 2.0 will freeze when I run an application. What do I
do?
(1.15) How can I get answers to my OS/2 questions?
(1.16) Why should I use HPFS? What does it offer me? Does it work with
DOS?
(1.17) I'm a Unix wizard. How do I make OS/2 resemble Unix?
(1.18) I prefer Windows. How do I make OS/2 2.0 resemble Windows (or OS/2
1.3)?
(1.19) I would like to set up an OS/2 BBS. What is available?
(1.20) Can I use COM3 and COM4 in OS/2 2.0?
(1.21) How do I start a background process from the OS/2 command line?
(1.22) What are CSDs, how do I tell which I have, and where do I get them?
(1.23) How do I add new Adobe Type Manager typefaces?
(1.24) How do I tweak OS/2 2.0 for maximum performance?
(1.25) What networking products are available for OS/2 2.0?
(1.26) Should I worry about viruses when running OS/2 2.0?
(1.27) Are there any clever tricks that apply to OS/2 2.0?
(1.28) What do I need for OS/2 multimedia applications?
(1.29) How do I measure OS/2 performance and memory usage?
(1.30) What can I do to promote OS/2?
(1.31) My background bitmap does not display correctly. What's wrong?
(1.32) What is the best way to partition my hard disk for OS/2?
(1.33) What are the "must have" shareware and freeware titles?
(1.34) Are there any specific hardware recommendations?
(1.0) What is OS/2?
What is OS/2?
OS/2 is an advanced operating system for PCs and PS/2s with an 80286
processor or better. It was codeveloped by Microsoft and IBM and
envisioned as the successor to DOS.
It was designed from the ground up with preemptive multitasking and
multithreading in mind. It also protects applications from one another (a
single misbehaved program will not typically disrupt the entire system),
supports all addressable physical RAM, and supplies virtual memory to
applications as requested, breaking DOS's 640K barrier.
As shipped, it does not support multiuser operation, although third parties
have grafted multiuser capabilities onto the base operating system. These
products include:
Software Title Company Telephone
Remote-OS Software Lifeline (407) 994-4466
OS2You ? See (1.7) Shareware and
Freeware Sources
Citrix Citrix Systems (305) 755-0559
PolyMod2 MemSoft ?
PC/DACS (Pyramid, phone 203-257-4223) offers security (for multiple users,
one at a time, in a lab setting for example).
Related information:
(1.1) Differences Between Versions
(1.2) Extended Services
(1.3) DOS and Windows Compatibility
(1.1) Differences Between Versions
What are the differences between versions?
IBM OS/2 Version 2.1 is currently in beta testing and is widely available
[See (1.7) Shareware and Freeware Sources]. This new version will support
Windows 3.1 applications, Windows enhanced mode, more third party adapters
and peripherals, and OS/2 multimedia applications.
IBM OS/2 Version 2.0 [CSD Level 06055; See (1.22) Corrective Service
Diskettes] will run only on machines with an 80386SX processor or better.
IBM is developing OS/2 (and its Intel and non-Intel-based successors)
independently but is involving third party PC manufacturers in its testing.
Improvements include an object-oriented Workplace Shell (WPS); a multiple
operating system boot mechanism; better DOS and Windows support [See (1.3)
DOS and Windows Compatibility]; new 32-bit programming interfaces; support
for more than 16 MB of physical RAM (on all systems with appropriate BIOS
support; memory above 16 MB on those systems which must rely on 24-bit DMA
for disk access, e.g. AT bus systems with Adaptec 154x SCSI adapters, is
used as swap space); and more third party device drivers. OS/2 1.x
applications, unmodified, still run under OS/2 2.0.
IBM OS/2 Version 1.3 is the last release of OS/2 to operate on PCs with
80286 CPUs. This version introduced built-in Adobe Type Manager (ATM),
providing scalable typefaces for screen and printer. Procedures Language/2
(REXX), a powerful batch-oriented programming language, became a part of
Standard Edition with this release. (A few OEMs are shipping Microsoft
OS/2 Version 1.3, but Microsoft has all but abandoned OS/2 development.)
OS/2 Version 1.2 was the first to incorporate the High Performance File
System (HPFS). With this release IBM OS/2 added a dual boot mechanism and
IBM Extended Edition introduced REXX.
OS/2 Version 1.1 was the first to include the Presentation Manager (PM)
GUI/API. Microsoft OEM versions added a dual boot mechanism with this
release.
OS/2 Version 1.0, introduced in 1987, was the first release of OS/2. Task
switching was accomplished using a character-based shell and limited DOS
compatibility was provided.
Related information:
(1.0) What is OS/2?
(1.2) Extended Services
(1.3) DOS and Windows Compatibility
(1.7) Shareware and Freeware Sources
(1.22) Corrective Service Diskettes
(1.23) Adobe Type Manager
(1.2) Extended Services
What is Extended Services?
Prior to Version 2.0, IBM offered two separate packages with each release
of OS/2: Standard Edition and Extended Edition. Extended Edition included
extra, bundled software products: the Communications Manager (for
communication with IBM mainframes, minicomputers, and other hosts),
Database Manager (a full, network aware, relational database), and LAN
Requester.
IBM has now unbundled the Extended Edition features, dropped LAN Requester
from the package (now available separately, with IBM's LAN Server), updated
it for OS/2 2.0, and renamed it Extended Services 1.0. ES, by itself, no
longer includes the base operating system as Extended Edition once did.
This new arrangement makes it easier to update the base operating system
with CSDs [See (1.22) Corrective Service Diskettes]. And now ES 1.0 will
run under OS/2 1.3 Standard Edition as well as OS/2 2.0. Also, ES 1.0,
like OS/2 2.0 itself, is designed to operate on both IBM and non-IBM
systems [See (1.5) Hardware Requirements].
Related information:
(1.1) Differences Between Versions
(1.5) Hardware Requirements
(1.22) Corrective Service Diskettes
(1.25) Networking Products
(1.3) DOS and Windows Compatibility
How good is OS/2 2.0's DOS and Windows compatibility?
OS/2 1.x justifiably earned a reputation for poor DOS compatibility. Since
it was hampered by the 80286, it could not run more than one DOS
application at a time.
The situation has changed dramatically with OS/2 2.0. Version 2.0
preemptively multitasks DOS and Windows (real and standard mode)
applications in separate, protected sessions, without purchasing either
environment.
OS/2 2.0 provides a complete DOS emulation equivalent to DOS 5.0. The
operating system can provide each DOS application with up to 32 MB of EMS
4.0 (expanded memory), 16 MB of XMS 2.0 (extended memory), and/or 512 MB of
DPMI 0.9 (DOS Protected Mode Interface extended memory), all from its pool
of physical and/or virtual memory (meaning you do not have to have as much
RAM in your system as your applications request). These limits are in
addition to the up to 730K free conventional memory supplied to each DOS
application, even after mouse and network drivers are loaded. As in DOS
5.0, DOS code and device drivers may be loaded into high memory. A 386
memory manager like QEMM is not needed -- these features are provided by
OS/2 2.0 directly.
The DOS emulation allows customization of device driver sets -- each DOS
application shares a systemwide CONFIG.SYS and the equivalent of its own
CONFIG.SYS. Also, there is a systemwide AUTOEXEC.BAT file; batch commands
particular to each DOS application can be invoked using separate,
application-specific batch files. And many DOS Settings are provided to
fine tune each DOS/Windows application's behavior (e.g. IDLE_SENSITIVITY).
Most of the popular DOS/Windows applications on your hard disk will be
migrated automatically when you install OS/2 2.0.
In addition, OS/2 2.0 will boot one or more specific versions of DOS in
separate sessions, to assist in running particularly difficult applications
(e.g. DOS networks, MSCDEX). So, for example, it is possible to multitask
DOS 3.3, DOS 4.0, DOS 5.0, emulated DOS, and Desqview running atop DOS, all
in separate sessions, either windowed or full screen, all with the same
and/or separate device drivers, TSRs, environment variables, etc. DOS boot
images may be stored on a hard disk. These procedures are described in the
online Command Reference (under VMDISK), Master Help Index, and in the
Installation Guide (Appendix E).
Standard graphics modes [generally up to the resolution of the desktop; See
(1.9) SuperVGA Support] are supported in DOS windows, as are selectable
text mode fonts. Cut/paste to/from windowed DOS applications is supported
(to/from other DOS, OS/2, and Windows applications), including graphics
cut/paste. Theoretically, OS/2 2.0 will run up to 240 simultaneous
DOS/Windows sessions; the practical maximum depends on system resources.
OS/2 2.0 will, in fact, run virtually all DOS applications in existence,
including notorious ones such as Microsoft Flight Simulator, Wing
Commander, Maple, MatLab (Ver. 3.5k or later), and others. Those that do
not run generally fall into the following categories:
1. Programs that use Virtual Control Program Interface (VCPI) memory
extenders or other extenders which require direct access to 80386 control
registers. Since such applications are also all but incompatible with
Windows, most vendors have updates for DPMI compatibility;
2. Applications which attempt to directly address the physical sectors of an
OS/2 managed nonremoveable hard disk drive. Such programs include UnErase
in Norton Utilities. Fortunately OS/2 2.0 has a built-in UnDelete feature
which is more robust than Norton's approach. (Consult the online Command
Reference for information on how to enable UNDELETE);
3. Timing sensitive DOS applications. Certain DOS programs that generate
digitized sound through the PC's internal speaker may have distorted sound.
High speed, real time data collection may be compromised. These problems
can often be minimized or even eliminated using OS/2 2.0's DOS Settings.
4. Certain DOS programming debuggers. DOS applications running under OS/2
2.0 are not permitted to access debug registers DR0-DR7 from a DOS session.
Also, DOS debuggers will not be able to set hardware breakpoints, and all
read/write operations to debug registers in virtual 8086 mode will be
ignored.
Generally DOS backup programs will work under OS/2 2.0, but they may not
capture some OS/2 data (especially extended attributes) on the hard disk
without the assistance of utilities such as EABackup [See (1.7) Shareware
and Freeware Sources].
OS/2 backup tools are available, notably:
Software Title Company Telephone
PMTape and PS2Tape IBM and Irwin (???) ???-????
Sytos Plus Sytron (508) 898-0100
EZTape Irwin (313) 930-9000
DMS/Intelligent Backup Sterling (916) 635-5535
FileSafe Mountain (408) 438-2665
KeepTrack Plus Finot (800) 748-6480
NovaBack NovaStor (818) 707-9900
OBackup ? See (1.7) Shareware and
Freeware Sources
BackMaster MSR Development (409) 560-5970
MaynStream Maynard (407) 263-3500
The OS/2 BACKUP utility is best used from an OS/2 diskette boot [See (1.11)
Starting OS/2 from Diskette]. DOS-based disk caching software is not
required since OS/2 includes a built-in, highly configurable, efficient
disk cache.
DOS programs running under OS/2 2.0 are extremely fast. A single DOS
application (no other applications open) running full screen under OS/2 2.0
typically achieves 95-97% of the performance it would have under native
DOS. If the DOS application performs any disk I/O it can actually operate
up to several times faster than it would if running under native DOS.
If pure DOS is absolutely required, OS/2 2.0 includes a utility called the
Boot Manager. The Boot Manager can provide a listing of all the operating
systems available on the system and will allow selection of any one at
startup, with a default after timeout. The OS/2 1.x DualBoot method is
still available as well. Consult the Installation Guide for instructions
on how to use Boot Manager or DualBoot. Note that OS/2 2.0 need not be
installed on Drive C -- it can reside on other volumes [See (1.32) Hard
Disk Partitioning].
Compatibility with Windows, a popular DOS extender, is provided by
Win-OS/2, an environment based on Microsoft's Windows source code. It runs
Windows 2.x and 3.0 real mode and standard mode applications under OS/2
2.0, either on a full screen Windows desktop (with the familiar Program
Manager and one or more Windows applications) or "seamlessly," alongside
OS/2 applications on the Workplace Shell desktop. "Seamless" operation is
available in VGA, Tseng 4000 SuperVGA, and XGA resolutions with OS/2 2.0 as
it ships.
Several icon conversion utilities can convert Windows icons for use by the
OS/2 Icon Editor and/or OS/2-specific programs [See (1.7) Shareware and
Freeware Sources]. (No conversion is necessary if the icons are to be used
with Windows programs running under OS/2 2.0.)
OS/2 2.0 directly provides Windows enhanced mode features save one:
services included in WINMEM32.DLL. Windows applications which utilize this
DLL (e.g. Mathematica 2.0, Omnipage Professional 1.0) will not run under
OS/2 2.0. Fortunately the number of WINMEM32 applications is few, and
apparently the vendors of such applications will be shipping OS/2 2.0
compatible updates.
Windows applications are well integrated into the overall OS/2 WPS
environment with DDE and Clipboard hooks, and OLE 1.0 is supported among
Windows applications. Adobe Type Manager for Win-OS/2 comes with OS/2 2.0.
Windows screen (for a full screen desktop) and printer device drivers will
work under Win-OS/2 [See (1.9) SuperVGA Support]. Such notorious Windows
applications as Word, Norton Desktop (save portions described above),
Toolbook, and After Dark work fine under Win-OS/2. Even the Windows
Multimedia Extensions (and programs which utilize them) operate under
Win-OS/2. [See (1.28) Multimedia for information on the OS/2 multimedia
extensions, MMPM/2.]
Win-OS/2 departs from Microsoft Windows in that it allows more than one
Windows desktop and can preemptively (rather than cooperatively) multitask
Windows applications in separate, robust, protected sessions. Also, while
many Windows 3.1 enhancements are functionally incorporated into Win-OS/2,
Win-OS/2 is not technically Windows 3.1 compatible. OS/2 2.1, due in early
1993, will incorporate Windows 3.1 support (including enhanced mode).
Fortunately there are few Windows 3.1-specific applications. Win-OS/2 will
run the Windows 3.0 applets, but it does not include them. Instead, true
OS/2 2.0 spreadsheet, database, communications, time planning/scheduling,
and other applets are provided.
Some Windows applications require OLE DLLs or custom settings in WIN.INI.
If such a Windows application has been installed under the DOS version of
Windows, Win-OS/2 may not be able to find the appropriate files or
configuration. Try reinstalling the Windows application under Win-OS/2.
Related information:
(1.1) Differences Between Versions
(1.7) Shareware and Freeware Sources
(1.9) SuperVGA Support
(1.11) Starting OS/2 from Diskette
(1.13) Disk Utilities
(1.23) Adobe Type Manager
(1.24) Performance Tuning
(1.25) Networking Products
(1.28) Multimedia
(1.32) Hard Disk Partitioning
(1.4) Availability and Cost of OS/2
Where can I buy OS/2, and how much does it cost?
In the U.S. IBM OS/2 Version 2.0 is available from most software dealers
(including Corporate Software, phone 800-677-4000) and directly from IBM
(phone 800-3-IBM-OS2, or 800-222-7257 for educational inquiries). The cost
is just $99. Discounts are available for multiple licenses and educational
purchases. (Call for details on upgrades from OS/2 1.x. In Canada call
800-465-1234 to order. In the U.K. call the OS/2 User Group at
0285-655888 or IBM at 0800-181182. In other countries, contact any IBM
dealer or office.)
OS/2 2.0 on 3.5 inch diskettes is part no. 84F7586. For 5.25 inch
diskettes, 10G2991. Media are high density. For compact disc, 10G2992.
IBM OS/2 Version 1.3 is still available and may be ordered through many IBM
dealers.
IBM is trying to make OS/2 2.0 available everywhere DOS is purchased. If
your dealer does not stock OS/2 2.0, take your business elsewhere (and
explain why). IBM bundles OS/2 2.0 with some PS/1, all but one ValuePoint,
and all 386SX (and above) PS/2 systems. Several other vendors, including
Dell, will preload OS/2 2.0 on request.
IBM offers two money back guarantees in the U.S.: a 30-day, no questions
asked, money back guarantee, and a 90-day compatibility guarantee (See
(1.5) Hardware Requirements).
Microsoft versions of OS/2 1.x are available only through OEMs (e.g.
Compaq and Dell) or by purchasing Microsoft's LAN Manager 2.1a or SQL
Server products. Microsoft has all but ceased OS/2 development, working
instead on Windows NT.
Related information:
(1.1) Differences Between Versions
(1.5) Hardware Requirements
(1.25) Networking Products
(1.5) Hardware Requirements
What hardware do I need to run IBM OS/2 2.0? Do I need a PS/2?
You need any PC compatible with at least an 80386SX CPU, 4 MB (6 MB or more
strongly recommended) of RAM, a 60 MB or larger hard disk (with 20-35 MB
free), a supported video adapter (CGA, EGA, VGA, Tseng 4000 SuperVGA,
8514/A, XGA, or third party driver) with appropriate display, and a high
density 3.5 or 5.25 inch floppy drive for installation. A mouse or other
pointing device is strongly recommended. Allow extra RAM and hard disk
space for OS/2-based networking, Extended Services, and/or extra system
loads (i.e. an extraordinary number of large applications running
simultaneously). When calculating hard disk space requirements, subtract
space occupied by files already on the hard disk which are functionally
included in OS/2 2.0 and may be deleted, e.g. DOS, a 386 memory manager,
Windows, Adobe Type Manager with base typefaces, etc.
The Workplace Shell (WPS) will not operate with the Monochrome Display
Adapter or the Hercules Monochrome Graphics Adapter. Usually the WPS will
fail to work with monochrome EGA. However, some EGA adapters (e.g.
Paradise Monochrome EGA Card, ATI EGA Wonder) will emulate all color EGA
modes on TTL monochrome monitors and, thus, will work with the WPS.
Certain dual monitor configurations are supported; consult IBM for advice.
On (E)ISA bus machines, OS/2 specifically supports hard drive adapters
which conform to the Western Digital chipset interface standard (nearly all
MFM, RLL, IDE, and ESDI adapters) and Adaptec, Future Domain, and IBM SCSI
adapters. (True OS/2 2.0 drivers for most SCSI adapters, e.g. Trantor,
DPT, Rancho, Procomp, Corel Systems, BusLogic, Mylex, CE Infosys, Ciprico,
and others are available directly from the adapter manufacturers. A driver
for the Always IN-2000 adapter is available by calling 818-597-1400.) In
addition, "generic" INT13 support is provided for all other hard disk
adapters. This "generic" support even embraces such devices as Iomega's
Bernoulli and SyQuest's removeable media products (but for best results
contact Iomega or SyQuest for an OS/2 2.0 driver).
CD-ROM support (for IBM CD-ROM drives; Hitachi models CDR-1650S, CDR-1750S,
CDR-3650, and CDR-3750; NEC models CDR-36, CDR-37, CDR-72, CDR-73, CDR-74,
CDR-82, CDR-83, and CDR-84; Panasonic models CR-501 and LK-MC501S; Texel
models DM-3021, DM-3024, DM-5021, and DM-5024; Toshiba models 3301T,
TXM3301, 3301B, and XM-3201; Pioneer DRM-604X; and Sony models CDU-541,
CDU-561, CDU-6111, CDU-6211, and CDU-7211; only when attached to IBM,
Future Domain, Adaptec, or other SCSI adapters with native OS/2 2.0
support) is available [See (1.7) Shareware and Freeware Sources]. Others
(e.g. Mitsumi) will follow. This support includes single session Kodak
Photo CD services for those drives which support the standard. (Storage
Devices and other companies offer OS/2 CD-ROM drivers for their products.
Corel Systems offers a set of drivers for many more CD-ROM drives and
adapters.) The DOS device drivers, when installed using a specific DOS
session, will still provide CD-ROM services to DOS/Windows programs for the
remainder. See (1.10) Printer Support for information on printer and
plotter compatibility.
Version 2.0 is explicitly supported on PC compatibles. IBM is offering a
money back compatibility guarantee in the U.S. Should OS/2 2.0 fail to
work on your compatible within the first 90 days of use, and should IBM be
unable to fix the problem, your purchase price will be refunded. To date
over 400 non-IBM models have been tested in IBM's own labs.
Related information:
(1.2) Extended Services
(1.7) Shareware and Freeware Sources
(1.23) Adobe Type Manager
(1.25) Networking Products
(1.6) Applications
What applications are available for OS/2?
In addition to the thousands of applications available for DOS and Windows,
there are a couple thousand OS/2-specific applications representing almost
every category imaginable.
The DOS/Windows applications with 16-bit OS/2-specific counterparts include
Lotus 1-2-3, Freelance, Notes, cc:Mail; Microsoft Word, Excel, Multiplan,
Mail; Aldus Pagemaker; Ventura Publisher; Corel Draw; WordPerfect;
DisplayWrite; DeScribe; Micrografx Designer; AutoCAD; Oracle; RBase; SAS;
SPSS; HyperAccess/5; DynaComm; Pro-YAM; Borland Sidekick, Paradox, Brief;
Wingz; QEdit; 4DOS; and many others. In some cases DOS and OS/2 versions
ship together (e.g. Microsoft Word 5.5, Lotus 1-2-3 3.0, Wingz).
OS/2 2.0 provides an attractive, 32-bit, Workplace Shell environment for
new applications; many do not have DOS/Windows predecessors. This new
class of 32-bit applications will (or does) include Lotus 1-2-3, Freelance,
cc:Mail, Notes, AmiPro; WordPerfect Corp.'s WordPerfect, Office,
Presentations; N/Joy; DeScribe; Publisher's Paintbrush; PFS:Works;
CorelDraw; HyperAccess; Faxworks; FAX/PM; all Micrographx applications;
RBase; Advanced Revelation; Norton Commander; and many more. Over 1100 new
32-bit OS/2 2.0 applications have been released to date.
OS/2-specific versions of popular utilities include ZIP/UNZIP, ARC, LH2,
Zoo 2.1, many GNU tools, tens of different file finders, desktop clocks,
calculators, and many more. Programming languages include Assembler, C++,
COBOL, Pascal, C, Fortran, BASIC, REXX (included with every copy of OS/2
2.0), Icon, Smalltalk, Modula-2, LISP, Forth, and still more, from vendors
such as Borland, Clarion, Watcom, Symantec (through its Zortech
subsidiary), IBM, Microway, and many more. Two free ports of the 32-bit
GNU C/C++ compiler, GCC/2 and EMX/GCC, are available [See (1.7) Shareware
and Freeware Sources]. Fortran to C (f2c) and Pascal to C (p2c)
translators are also available. (See the Programmer's Edition of this List
for more information.)
The IBM NSC BBS (404-835-6600) provides an online product database of
OS/2-specific software. A directory of OS/2 applications, IBM document
number G362-0029-02, is published by Graphics Plus (phone 800-READ-OS2).
TINF [See (1.7) Shareware and Freeware Sources] is an applications
directory (for use with the OS/2 VIEW facility).
Related information:
(1.3) DOS and Windows Compatibility
(1.7) Shareware and Freeware Sources
(1.7) Shareware and Freeware Sources
Where can I obtain OS/2 shareware and freeware?
The following BBSes hold large OS/2 libraries:
Fernwood (203) 483-0348
OS/2 Shareware (703) 385-4325
Bay Area OS/2 (510) 657-7948
Gateway/2 (314) 554-9313
Greater Chicago Online (708) 895-4042
OS/2 San Diego (619) 558-9475
OS/2 Las Vegas (702) 433-5535
IBM Germany 049-711-785-7777
IBM Denmark 45-42-88-72-22
OS/2 UK 0454-633197
IBM UK 0256-336655
IBM Norway 47-22-99450
OS/2 Australia 61-2-241-2466
(The monthly Worldwide OS/2 BBS Listing, available from these BBSes, lists
others.) The IBM NSC BBS (modem 404-835-6600) has some shareware/freeware
as well, along with CSDs [See (1.22) Corrective Service Diskettes] and the
PS/2 Assistant (an invaluable resource for locating almost any sort of
information on OS/2). For information on IBM's new OS/2 BBS call
800-547-1283. IBM Canada maintains several support BBSes:
(416) 946-4255
(514) 938-3022
(604) 664-6464
(416) 946-4244
The Usenet conference comp.binaries.os2 carries OS/2 software. And several
sites are available via anonymous ftp. (No ftp? Send a single line
message with the word HELP to bitftp@pucc.bitnet or ftpmail@decwrl.dec.com
to learn about ftp mail servers.) Some are (with Internet node numbers and
subdirectories):
ftp-os2.nmsu.edu 128.123.35.151 pub/os2
software.watson.ibm.com 129.34.139.5 pub/os2
mtsg.ubc.ca 137.82.27.1 os2:
access.usask.ca 128.233.3.1 pub/archives/os2
luga.latrobe.edu.au 131.172.2.2 pub/os2
funic.funet.fi 128.214.6.100 pub/os2
pdsoft.lancs.ac.uk 148.88.64.2 micros/ibmpc/os2
ftp.uni-stuttgart.de 129.69.1.12 soft/os2
src.doc.ic.ac.uk 146.169.2.1 computing/systems/os2
The ftp-os2.nmsu.edu library is available on CD-ROM from Walnut Creek
(phone 510-947-5996). EMS (call 301-924-3594) offers an OS/2
shareware/freeware library on diskettes.
Other sources include CompuServe (FIND OS/2) and archive servers (send a
single line message with the word HELP to listserv@cc1.kuleuven.ac.be or
mail-server@rus.uni-stuttgart.de for more information, or use ftp).
IBM has been releasing freely distributable employee written software (e.g.
Visual REXX) and OS/2 patches to these sites.
Related information:
(1.19) Running a BBS Under OS/2
(1.22) Corrective Service Diskettes
(1.26) Viruses
(1.33) "Must Have" Shareware and Freeware
(1.8) Installation
I am having trouble installing OS/2 2.0. What should I do?
First consult the Installation Guide and other materials accompanying OS/2
2.0. Make sure your PC meets the system requirements in (1.5) Hardware
Requirements.
And if the following instructions do not help, fall back on IBM's toll free
technical support (call 800-237-5511 in the U.S.) and/or consult IBM's
Tips and Techniques file [See (1.7) Shareware and Freeware Sources].
o Certain PC compatibles have difficulty accepting OS/2 2.0 [CSD level 02000
only; See (1.22) Corrective Service Diskettes], particularly AT bus systems
with RLL, MFM, or ESDI adapters. The problem usually appears in the form
of FDISK errors, extremely slow copying to the hard disk, or a
whining/grating noise emanating from the hard disk. A replacement
IBM1S506.ADD file alleviates the problem [See (1.7) Shareware and Freeware
Sources].
o When installing, the Logitech Mouse selection should be chosen only if you
have a Mouse Systems PC Mouse (or compatible, e.g. certain Genius models)
or a Logitech C7 or C9 serial mouse. (If you have another Logitech
pointing device, it is likely Microsoft compatible when powered up, so
select the appropriate Microsoft driver, e.g. "Serial Pointing Device.")
If you are using a Logitech C7 or C9 serial mouse and have been using
native DOS, be sure to issue the command MOUSE PC (or MOUSE 2 PC if your
mouse is attached to COM2) before booting into or installing OS/2.
Alternatively, turn off the system (to reset the mouse) before booting or
installing OS/2.
o Some PCs have trouble printing under OS/2 2.0. This problem can often be
traced to an interrupt conflict, a substandard cable, an interfering
software security "dongle," or a faulty printer adapter. LPT1 uses IRQ 7,
and LPT2, if installed, uses IRQ 5. Interrupts should not be shared on AT
bus machines. The SoundBlaster, for example, comes set to IRQ 7. Reset it
to an unused interrupt.
o Make sure adapters with onboard ROMs are not conflicting with other
adapters. For example, many SuperVGA adapters use large segments of upper
memory, and many hard disk adapters have onboard ROMs which can be mapped
into the same areas. Adapters must not share address space or interrupts.
Check your product manuals for more help.
o Be sure adequate free disk space is available before installing, including
space for a swap file. Drives compressed using Stacker or similar
utilities should be uncompressed before installing (unless access to these
drives from OS/2 is not needed). An OS/2 2.0 version of Stacker is
forthcoming, and Proportional Software's (phone 303-484-2665) DCF/2, a
Stacker-like utility, is also due to ship soon.
o Do not select HPFS when installing if your machine has 6 MB of RAM or
less, or diminished performance will likely result. Change the IFS=...HPFS
line in your CONFIG.SYS to REM IFS=... if necessary.
o Automatic migration of your DOS CONFIG.SYS and AUTOEXEC.BAT files is not
recommended. If you have Windows 3.1 installed on your system do not
migrate your Windows desktop.
o Be sure your CMOS setup parameters are set correctly, especially those
relating to floppy drives. RAM should be given sufficient wait states and
precharge cycles. Test with cache memory and/or shadow RAM disabled if
necessary. The AT bus should run at 8 MHz.
o If you are using the IBMINT13.I13 driver to access an MFM, RLL, or ESDI
hard drive, and the hard drive has more than 1024 cylinders, be certain
your hard disk adapter's sector translation mode is enabled.
o Some Quantum LPS105AT IDE hard disks require a free ROM update (to Version
2.6) from the manufacturer to work with OS/2.
o If your AMI keyboard BIOS is below Revision F you may need an update.
Contact Washburn & Assoc. (phone 716-248-3627).
o Check to make sure keyboard DIP switches are set correctly. For example,
if the keyboard is attached to a system with an AT bus it should typically
be switched to "AT" mode.
o "Autoswitching" on non-IBM EGA adapters should be disabled (usually with a
DIP switch or jumper setting). In rare cases it may be necessary to switch
third party VGA/SuperVGA adapters into 8-bit mode and/or disable
"autosense." See (1.09) SuperVGA Support.
o OS/2 is particularly sensitive to bad RAM or cache memory (often reflected
in TRAP 0002 error messages). Use a thorough RAM testing utility, and try
not to mix 9-chip and 3-chip SIMM/SIPP memory modules.
o A driver for HP DeskJet printers, including color models, is available for
download. See (1.7) Shareware and Freeware Sources.
o Allow several minutes for OS/2 2.0 to build your desktop (and display
icons) at the end of installation -- take the Tutorial offered to you in
the meantime. Select Shutdown and reboot once after installation completes
to ensure that DOS/Windows applications will operate properly. Avail
yourself of the "Start Here" icon, the Welcome folder (if applicable), the
other online help, and the README file located in the root directory. They
will help in getting started with the Workplace Shell and in properly
configuring your system.
o When installing over a beta version of OS/2 (except OS/2 2.0 level 6.177H,
the Limited Availability release) be sure to reformat.
o To install the Upgrade Version of OS/2 2.0, DOS or OS/2 must already
reside on the hard disk. If Diskette 1 is not write protected then the
installation program will record a file indicating that upgrade terms have
been satisfied and, in the future, will not require DOS or OS/2 on the hard
disk to install.
o OS/2 uses the same diskette format as DOS, so use DISKCOPY to backup the
installation diskettes and verify that none have been corrupted.
o Owners of IBM PS/2s should make sure that any applicable ECAs (engineering
changes) have been performed and that the most recent Reference Diskette is
in use. Reference Diskettes are available from the IBM NSC BBS (modem
404-835-6600).
o Try disconnecting any tape backup device if "Cannot find COUNTRY.SYS"
messages are encountered when booting OS/2.
o Contact IBM for a fix to install OS/2 2.0 [CSD level 02000 only; See
(1.22) Corrective Service Diskettes] on certain Zeos notebooks.
o An Always IN-2000 SCSI adapter with BIOS 3.06A or 3.20 requires an updated
version from the manufacturer. A companion 8-pin serial PROM chip may also
need to be updated. Contact Always at 818-597-9595. Also ask about
non-IBMINT13.I13 driver support.
o The TI TM4000 notebook may require a BIOS update to run OS/2 2.0; call
817-771-5856 for help.
Related information:
(1.5) Hardware Requirements
(1.7) Shareware and Freeware Sources
(1.9) SuperVGA Support
(1.22) Corrective Service Diskettes
(1.9) SuperVGA Support
Will OS/2 2.0 work with my SuperVGA adapter?
If you have a SuperVGA adapter, OS/2 2.0 should initially be installed
using the standard VGA driver. Then consult the README file OS/2 copies to
your root directory for more information on SuperVGA support.
OS/2 2.0 comes with basic mode switching capabilities to handle
applications which utilize SuperVGA modes. If OS/2 2.0 detects a SuperVGA
adapter it will list two SuperVGA support files, VSVGA.SYS and BVHSVGA.DLL,
in your CONFIG.SYS file. [A replacement VSVGA.SYS file, dated April 20,
1992, or later, fixes Tseng 4000 and TRAP 000E problems. A replacement
BVHSVGA.DLL file, dated April 21, 1992, or later, fixes C0000005 errors
involving Western Digital/Paradise chipset adapters. See (1.7) Shareware
and Freeware Sources.]
To enable this mode switching support, available for most SuperVGA
adapters, you must start a DOS full screen session, issue the command SVGA
ON, EXIT, Shutdown, and reboot. (In the same DOS full screen session and
prior to SVGA ON you may run utilities which customize refresh rates. The
new refresh rates will take effect after you reboot. You may also wish to
run such a utility from AUTOEXEC.BAT.) SVGA ON creates a text file called
\OS2\SVGADATA.PMI which describes your SuperVGA adapter to the system.
Then you may install high resolution drivers.
Aside from DOS applications (which may require their own drivers), OS/2 2.0
requires up to three high resolution support files:
\OS2\DLL\DISPLAY.DLL Workplace Shell display driver
\OS2\MDOS\WINOS2\SYSTEM\VGA.DRV Win-OS/2 full screen driver
\OS2\MDOS\WINOS2\SYSTEM\SWINVGA.DRV Win-OS/2 "seamless" driver
You may replace any one of these individually for high resolution operation
in each given mode, but be sure to keep a backup copy of the original
file(s). The "seamless" Win-OS/2 and WPS desktop driver files must match
(in terms of resolution and number of colors) if you wish to run Windows
programs "seamlessly." Any suitable Windows SuperVGA driver will work as a
Win-OS/2 full screen driver, but be sure to use the EXPAND utility (as
described in README) when installing.
OS/2 1.3 SuperVGA drivers often serve, with some limitations, as Workplace
Shell desktop drivers. Use the command DDINSTAL to replace DISPLAY.DLL.
Setting IOPL=YES in CONFIG.SYS may be required with a SuperVGA adapter.
CAUTION: For OS/2 2.0 CSD level 06055, \OS2\DLL\DISPLAY.DLL should not be
replaced, using DDINSTAL or otherwise. Instead, create a separate
directory (e.g. \DISPLAY) and copy the vendor supplied 16-bit driver DLL
file to \DISPLAY\DISPLAY.DLL. In CONFIG.SYS, place the \DISPLAY pathname,
including drive letter, before \OS2\DLL in the LIBPATH line. The exception
to this procedure is Tseng 4000 SuperVGA. To install any of the available
256 color Tseng 4000 SuperVGA drivers, use OS/2 System -> System Setup ->
Selective Install. Check the Primary Display box, reselect SuperVGA, then
proceed.
Drivers for the following SuperVGA adapters (or adapters based on these
chipsets) are available (A=all modes supported; B=most or some modes
supported; C=one mode supported; S=supports "seamless" Win-OS/2 in at least
one mode; X=experimental or beta). In most cases the drivers are available
from (1.7) Shareware and Freeware Sources.
Trident Series B S
Tseng Labs ET4000 B S
Compaq QVision B
Genoa 7000 B
ATI VGA Wonder Series B S X
ATI Ultra and Vantage Series B
Lava Computer (call 416-674-5942) B S
Orchid Farenheit (S3-based) B
Paradise/Western Digital B S X
Video7/Headland VRAM II B S X
Cirrus Logic B
Actix Systems (call 408-986-1625) ?
Number Nine (call 617-674-0009) ?
Portacom (call 415-390-8507) ?
"Generic" 800x600 16 color (VGA800-1) C
In addition, several vendors, notably Ahead (call 510-623-0900) and Radius
(call 408-434-1010), are readying XGA-2 compatible display adapters for
market. TIGA adapter support is available from Janus Systems (call
805-484-9770).
Consult adapter vendors for up-to-date information on driver availability.
Some SuperVGA adapters cause problems with DOS/Win-OS/2 sessions. Try
turning VIDEO_ROM_EMULATION off, HW_ROM_TO_RAM on, and/or DOS_RMSIZE to 624
in DOS Settings.
If you have an ATI Ultra, Vantage, or other 8514/A hardware compatible
adapter, install OS/2 using the 8514/A driver. With the Ultra Plus and
Ultra Pro adapters, make sure you set the monitor type to VGA using the
supplied ATI setup diskette before you install OS/2. You may still use
customized refresh rates for high resolution modes, but the adapter must
report the monitor type as VGA (or 8514/A) to OS/2.
IBM was unable to test all SuperVGA adapters, so if you are experiencing
problems report them through IBM's toll free support (call 800-237-5511 in
the U.S.) and to the adapter manufacturer.
If SuperVGA continues to cause problems the stock VGA driver may be used
(preventing DOS/Windows applications from using SuperVGA modes, however).
In CONFIG.SYS change DEVICE=...VSVGA.SYS to ...VVGA.SYS and SET
VIO_VGA...(BVHVGA,BVHSVGA) to ...(BVHVGA). This procedure may be required
for first generation SuperVGA adapters based on Trident 8800 and Tseng 3000
chipsets, for example.
OS/2 2.0's installation program (CSD level 02000 only) has difficulty with
certain Oak video adapters. Temporarily replace the video adapter to
install OS/2, or contact IBM for a patch.
Related information:
(1.7) Shareware and Freeware Sources
(1.22) Corrective Service Diskettes
(1.31) Displaying Background Bitmaps
(1.34) Specific Hardware Recommendations
(1.10) Printer Support
Will OS/2 2.0 work with my printer?
OS/2 2.0 includes support for Hewlett-Packard LaserJets, DeskJets [See
(1.8) Installation], and PaintJets; IBM/Lexmark ExecJets, InkJets,
Proprinters, Quickwriters, Quietwriters, Pageprinters, and Laserprinters;
Epson dot matrix and laser printers; Postscript devices; and other printers
(e.g. Panasonic) compatible with these families. A variety of IBM and HP
plotters is also supported.
DOS/Windows printer drivers continue to work for DOS/Windows applications.
OS/2 2.0 includes a large assortment of Windows printer drivers for
Win-OS/2. If necessary install Windows printer drivers using the Win-OS/2
Control Panel. OS/2 2.0 and OS/2 1.3 printer drivers are interchangeable
in many cases.
If your printer is not compatible with one of the drivers supplied with
OS/2, check with the printer manufacturer first then with (1.7) Shareware
and Freeware Sources. If you own an IBM printer, check with the Lexmark
BBS (modem 606-232-5653). The Lexmark/IBM 4070 InkJet driver, for example,
will also work with Canon BubbleJet printers.
Related information:
(1.7) Shareware and Freeware Sources
(1.8) Installation
(1.11) Starting OS/2 from Diskette (and CHKDSK)
How do I access HPFS partitions on my hard drive without booting from the
hard drive? I'm getting error messages now -- how do I "repair" my hard
disk?
With IBM OS/2 2.0, insert the Installation Diskette, Shutdown (if
necessary), and reboot. When prompted insert Diskette 1 and press ENTER.
When prompted, press ESC. You will be given an OS/2 command line prompt.
From there you can make necessary changes to your hard disk -- an OS/2
character mode text editor on diskette is handy for such changes. (Make
sure you backup CONFIG.SYS before making any changes so that you can easily
revert to the old version should things go wrong.)
You may use this diskette boot method to run CHKDSK on your FAT or HPFS
volumes. After you reach the command line, insert Diskette 2. Do not log
to another drive. Type CHKDSK X: /F to repair most kinds of damage to
your hard disk, replacing X with the appropriate drive letter. (If you are
checking a HPFS disk, use /F:3 if you have the time.) OS/2 CHKDSK will
also mark your hard disk as accessible, if possible, should OS/2 "lock it
out" for some reason. It will also allow Workplace Shell drive objects to
open properly if they are not functioning correctly.
"Errors" may be reported by CHKDSK if OS/2 was booted from the hard disk.
These "errors" are normal. Since the hard drive is in use by OS/2 itself
(and files are open) CHKDSK is unable to accurately report errors.
The best way to avoid the need to perform CHKDSK is to always select
Refresh then Shutdown. Click on the Workplace Shell desktop background
using mouse button two to bring up the appropriate menu. Also, avoid
manipulating OS/2-related files when using native DOS. Finally, enable
autochecking for all your hard disk volumes. For HPFS volumes use the
/AUTOCHECK parameter in the IFS=...HPFS line in your CONFIG.SYS. For FAT
volumes use the AC parameter in the DISKCACHE line of your CONFIG.SYS. See
the online Command Reference for details.
Several utilities [including SE20BOOT; See (1.7) Shareware and Freeware
Sources] can create a single, bootable OS/2 diskette (as a convenience).
Preloaded versions of OS/2 2.0 can create a bootable diskette pair from the
Welcome folder. (This step, along with a full BACKUP after a diskette
boot, should be performed immediately upon receipt of any IBM preloaded
OS/2 2.0 system.)
IBM has released a patch (UHPFS) which remedies "CPS: Extent" errors on
HPFS volumes. This patch is available from (1.7) Shareware and Freeware
Sources.
Related information:
(1.7) Shareware and Freeware Sources
(1.16) High Performance File System
(1.12) Installing from Drive B
I can't install OS/2 2.0 from Drive B. What's wrong?
IBM OS/2 2.0 can only be installed from Drive A, like DOS (unless your BIOS
supports booting from Drive B), or across a network (see Remote
Installation and Maintenance, IBM Publication No. GG24-3780-00). If you
have the wrong disk size go back to your dealer and obtain the correct
media. Otherwise you could open your machine and swap floppy drive cable
connectors, use your system's setup utility to set the new CMOS parameters,
and then install OS/2 from the "new" Drive A. Sometimes the floppy drive
cable connectors will not be the same. If so you can obtain an adapter
plug.
You may also use IBM's twin "bootstrap" diskette images [See (1.7)
Shareware and Freeware Sources] to boot from a 5.25 inch Drive A and
install using 3.5 inch OS/2 diskettes inserted into Drive B. This procedure
should only be used if absolutely necessary.
Related information:
(1.7) Shareware and Freeware Sources
(1.8) Installation
[End of Part One. Continue with Part Two.]
--
Timothy F. Sipples | READ the OS/2 FAQ List 2.0j, available from
sip1@ellis.uchicago.edu | 128.123.35.151, anonymous ftp, in /pub/os2/all/info
Dept. of Econ., Univ. | /faq, or from LISTSERV@BLEKUL11.BITNET (send "HELP")
of Chicago, 60637 | [Post to ONE newsgroup only AFTER reading the List.]